Skip to content

feat: add .NET 10 preview Lambda container image #2087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Jun 12, 2025
Merged

feat: add .NET 10 preview Lambda container image #2087

merged 2 commits into from
Jun 12, 2025
+401 −299

Conversation

philasmar
Copy link
Contributor

Issue #, if available:
DOTNET-8071

Description of changes:

  • Moved self-mutating step from each OCI pipeline to a parent pipeline. This will allow us to add new pipelines in the future with a PR instead of requiring an MCM.
    image
  • Added .NET 10 images
  • Updated the GitHub action to add .NET 10 as well as fix a bug in the script which didn't work for .NET preview versions
  • Updated Docker images to the latest .NET patches 8.0.17, 9.0.6, 10.0.0-preview.5
  • Removed .NET 6 images
  • .NET 10 images use the bootstrap.sh version with the SSL certificate updates which were required for .NET 8/9
  • Moved .NET version configurations to code instead of environment variables. This will allow us to add/remove .NET versions using a PR instead of an MCM.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@philasmar philasmar requested review from normj and GarrettBeatty June 12, 2025 14:37
@philasmar philasmar added the Release Not Needed Add this label if a PR does not need to be released. label Jun 12, 2025
GarrettBeatty
GarrettBeatty reviewed Jun 12, 2025
View reviewed changes
Copy link
Contributor

@GarrettBeatty GarrettBeatty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a different branch for when it gets deployed into staging vs prod account?

@philasmar
Copy link
Contributor Author

is there a different branch for when it gets deployed into staging vs prod account?

No, its just master. Once we get this merged in, we still need to run an MCM to release this. From that point onwards, the self-mutating pipeline will autoupdate once things hit master. As for staging, we don't have an automated process for it.

@philasmar philasmar merged commit 0d5ec2e into dev Jun 12, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@normj normj normj approved these changes

@GarrettBeatty GarrettBeatty GarrettBeatty approved these changes

Assignees
No one assigned
Labels
Release Not Needed Add this label if a PR does not need to be released.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@philasmar @normj @GarrettBeatty